feat: fire openCashLink eagerly on cold start instead of waiting for nav transition#970
Merged
Merged
Conversation
…nav transition On cold launch with a cash link deep link, openCashLink was deferred until the Loading → Scanner nav transition completed and App.kt's LaunchedEffect re-fired. This added visible latency before the bill appeared. Now buildNavGraphForLaunch carries a pendingAction for OpenCashLink and Login deep links, and MainRoot fires it immediately alongside the nav transition so the claim starts in parallel with the Scanner screen appearing. Signed-off-by: Brandon McAnsh <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On cold launch with a cash link deep link, openCashLink was deferred until the Loading → Scanner nav transition completed and App.kt's LaunchedEffect re-fired. This added visible latency before the bill appeared.
Now buildNavGraphForLaunch carries a pendingAction for OpenCashLink and Login deep links, and MainRoot fires it immediately alongside the nav transition so the claim starts in parallel with the Scanner screen appearing.